Budgeting and quota management system for data consumption

ABSTRACT

Systems and methods may provide for establishing a data usage budget based on one or more of user input and historical usage data, wherein the data usage budget distinguishes between usage types and distinguishes between connection types. Additionally, a data usage of one or more client devices may be monitored in accordance with the data usage budget. In one example, the usage types are designated as one or more of a high bandwidth usage and a low bandwidth usage, and the connection types are designated as one or more of a capped connection and a non-capped connection.

TECHNICAL FIELD

Embodiments generally relate to data consumption management. Moreparticularly, embodiments relate to data consumption budgeting and quotamanagement solutions.

BACKGROUND

Mobile devices may be increasingly able to consume large amounts of datain the form of video streaming, audio streaming and downloads, whereinusers may have little or no information regarding device dataconsumption levels. As a result, a user may encounter extra fees if dataconsumption levels exceed the data plan limit to which she device issubscribed. Alternatively, the user may underuse data consumption on adevice in an effort to avoid such extra fees—effectively overpaying fordata service. This difficulty may be even more significant when thedevice engages in different types of data usage via different connectiontypes, and when billing complexity increases due to the data plancovering multiple devices.

BRIEF DESCRIPTION OF THE DRAWINGS

The various advantages of the embodiments will become apparent to oneskilled in the art by reading the following specification and appendedclaims, and by referencing the following drawings, in which:

FIG. 1 is a block diagram of an example of a compute continuum accordingto an embodiment;

FIG. 2 is an illustration of an example of a budgeting and quotamanagement user interface according to an embodiment;

FIGS. 3A and 3B are illustrations of examples of advanced setting userinterfaces according to embodiments;

FIG. 4 is a flowchart of an example of a method of budgeting data usageaccording to an embodiment;

FIG. 5 is a block diagram of an example of a computing device accordingto an embodiment;

FIG. 6 is a block diagram of an example of a processor according to anembodiment; and

FIG. 7 is a block diagram of an example of a system according to anembodiment.

DESCRIPTION OF EMBODIMENTS

Turning now to FIG. 1, a “compute continuum” 10 is shown for a pluralityof client devices 12 (12 a-12 f), wherein the client devices 12use/consume data via different connection types. For example, a wireless“flip” phone 12 a and a wireless “smart” phone 12 b may, at a givenmoment in time, consume data via a connection to a cellular tower 14(e.g., third generation/3G, fourth generation/4G), wherein the cellulartower 14 may be owned and/or operated by a particular service provider(e.g., cellular service provider, “Provider A”) offering a data planthat covers all of the client devices 12. Thus, the connectionassociated with the cellular tower 14 and Provider A may be “capped” inthe sense that the client devices 12 may have a periodic allotment ofdata usage (e.g. 2 GB per month) that is covered by the basesubscription rate. In such a case, if the allotment of data usage isexceeded, the subscriber may be subject to additional “overage” feesand/or costs.

By contrast, the wireless smart phone 12 b and a smart tablet 12 c mayconsume data via a public networking connection to a public wirelessaccess point (WAP) 16. In such a case, the public wireless access point16 might be owned and operated by as entity (e.g., Internet café,restaurant, airport, etc.) having a data plan with a different serviceprovider (e.g., Internet service provider, “Provider B”), whereinoverage costs and/or usage allocations of the data plan with Provider Bare not passed on to the users of the client devices 12. Accordingly,the public networking connection associated with the public WAP 16 andProvider B may be considered to be “non-capped”.

Additionally, the illustrated smart tablet 12 c consumes data via aprivate networking connection to a private WAP 18, which may be in turnconnected to a modem 20 associated with another service provider (e.g.,cable and/or digital subscriber line/DSL provider, “Provider C”).Similarly, a landline telephone 12 d may consume data via a connectionto the modem 20, a notebook computer 12 e may consume data via aconnection to the private WAP 18, the modem 20 and/or a wireless router22, and a desktop computer 12 f may consume data via a connection to thewireless router 22. In the illustrated example, the wireless router 22is also connected to the modem 20 associated with Provider C, whereinProvider C may also offer a data plan that covers all of the clientdevices 12. The data plan may have a periodic allotment of data usage(e.g., 250 GB per month) that is covered by the based subscription rate(yet potentially different from the data usage allotment of Provider A).In such a case, the subscriber may be subject to additional overage feesand/or costs if the data usage of the client devices exceeds theallotment. Accordingly, the private networking connection with the modem20 and Provider C may be considered to be a capped connection. Simplyput, the illustrated compute continuum 10 involves different connectiontypes (e.g., “capped” connection, “non-capped” connection) for theclient devices 12.

Of particular note is that the data usage by the client devices 12 mayalso be of a variety of different types. For example, the wireless flipphone 12 a may send and/or receive messages such as, for example, e-mailmessages, text messages, instant messages, and so forth, via the cappedconnection to the cellular tower 14, whereas the wireless smart phone 12b might download relatively large files (e.g., installation files,documents) via the non-capped connection to the public WAP 16.Similarly, the smart tablet 12 c may conduct video streaming activityvia the capped connection to the modem 20 and the notebook computer 12 emay conduct audio streaming activity via the capped connection to themodem 20. The data usage by the client devices 12 may therefore rangefrom “high bandwidth” (e.g., downloading activity, streaming activity)to “low bandwidth” (e.g., messaging activity) usage.

As will be discussed in greater detail, a cloud-based budgeting system24 may provide for establishing and managing data usage budgets thatdistinguish between usage types and connection types in order to enablethe client devices 12 to achieve optimal data usage with respect to thevarious data plans covering the client devices 12. While the illustratedbudgeting system 24 is implemented at the cloud level (e.g., remoteserver, central data repository, etc.), the budgeting system 24 may beimplemented elsewhere in the compute continuum 10 to address privacy,security, architectural, performance, business model and/or marketingconcerns.

For example, FIG. 2 shows a user interface 26 (26 a-26 d) that enablesbudgets and/or quotas to be established and managed for data consumptionon a connection type basis as well as a usage type basis. In theillustrated example, a target usage panel 26 a prompts a user formonthly data usage amounts for downloading activity, video streamingactivity, music streaming activity and e-mail messaging activity. Thus,the user may set relative targets for different usage types. Theillustrated panel 26 a also enables the user to determine anyassumptions made with regard to the usage amounts chosen (e.g., “20min=˜100 MB”). The user interface 26 may also include a usage mode panel26 b that enables allocations to be suggested based on the usage mode(e.g., casual entertainment, work, vacation, etc.).

Additionally, a summary panel 26 c may indicate the total amount of datausage remaining based on a given total allotment. Moreover, a warningspanel 26 d may provide the user with the ability to receive variouswarnings for various events such as, for example, category allocationsbeing exceeded, available allotments falling below a specified level,and so forth. Other warnings may also be configured via the warningspanel 26 d. The content of the user interface 26 and/or its individualpanels may be specific to a particular service provider/data plan orapplicable across all associated service providers/data plans.

Turning now to FIGS. 3A and 3B, more advanced budgeting solutions areshown. In particular, FIG. 3A shows an advanced setting user interface28 (e.g., tab) that enables the user to configure a capped connection(e.g., 3G/4G) based on the type of usage. For example, the user may begiven the option to prevent client devices from engaging in highbandwidth usage activities such as music streaming, video streamingand/or downloads, when the client devices are using a 3G/4G network.Similarly, FIG. 3B shows an advanced setting user interface 30 (e.g.,tab) that enables the user to configure a non-capped connection (e.g.,public Wireless Fidelity/Wi-Fi) based on the type of usage. For example,the user may be given the option to prevent non-capped (e.g., publicWi-Fi) usage from being added to total consumption calculations,receiving a warning when leaving a non-capped connection whileconducting high bandwidth activities, ceasing high bandwidth activitieswhen leaving a non-capped connection, and so forth. Other customizationssuch as enabling the automatic resumption of high bandwidth activitieswhen re-entering a non-capped connection may also be configured via theadvanced settings user interface 30.

Turning now to FIG. 4, a method 32 of budgeting data usage is shown. Themethod 32 may be implemented in a computing device as a set of logicinstructions and/or firmware stored in a machine- or computer-readablemedium such as random access memory (RAM), read only memory (ROM),programmable ROM (PROM), flash memory, etc., in configurable logic suchas, for example, programmable logic arrays (PLAs), field programmablegate arrays (FPGAs), complex programmable logic devices (CPLDs), infixed-functionality logic hardware using circuit technology such as, forexample, application specific integrated circuit (ASIC), complementarymetal oxide semiconductor (CMOS) or transistor-transistor logic (TTL)technology, or any combination thereof. For example, computer programcode to carry out operations shown in the method 32 may be written inany combination of one or more programming languages, including anobject oriented programming language such as C++ or the like andconventional procedural programming languages, such as the “C”programming language or similar programming languages. Moreover, themethod 32 may be implemented using any of the aforementioned circuittechnologies.

Illustrated processing block 34 provides for prompting a user for inputregarding targeted data usage, wherein user input may be received atblock 36. The prompt at block 34 may be generated via a user interface(UI) such as, for example, the user interface 26 (FIG. 2), the userinterface 28 (FIG. 3A) and/or the user interface 30 (FIG. 3B), alreadydiscussed. Historical usage data may also be received at block 38. Thehistorical usage data may include data related to past data consumptionpatterns of one or more client devices, wherein the patterns may reflectthe type of connection, type of usage, etc., or any combination thereof.

Block 40 may establish a data usage budget that distinguishes betweenusage types as well as between connection types. For example, the datausage budget might designate target allocations for high bandwidth usageversus low bandwidth usage, capped connections versus non-cappedconnections, work-related usage versus casual entertainment usage, etc.,or any combination thereof. Data usage for one or more client devicesmay be monitored at block 42. Monitoring the data usage may include, forexample, obtaining metering information (e.g., consumption data andrelated metadata) from the client devices and/or one or more serviceproviders.

Of particular note is that the ability to obtain metering informationfrom multiple client devices that are subject to the same data plan maybe particularly advantageous given the multi-device lifestyles led bymany individuals, families and groups. Moreover, the ability to obtainmetering information from service providers may facilitate thevalidation and synchronization of metering information obtained from theclient devices. In the event that a service provider does not make themetering information readily available, a user might authorize thirdparty periodic access to a web account with the service provider inorder to obtain the metering information. The metering information maybe pushed by or pulled from the client devices and/or service providers.

Illustrated block 44 provides for generating one or more optimizationrecommendations based on the monitored data usage. The optimizationrecommendations may include, for example, a recommendation to cease orotherwise decrease the current data usage by one or more client devicesif the current data usage is designated as high bandwidth usage and thecurrent type of connection is a capped connection (e.g., cellularconnection, private networking connection). In such a case, it may beinferred that the current activity poses a risk of overage fees. Inanother example, the optimization recommendations may include arecommendation to begin or otherwise increase data usage if a billingcycle threshold is reached and a data usage threshold is not reached(e.g., the subscriber is about to end a billing cycle with unused dataallocation). Block 46 may implement the approved optimizations. One ormore of the optimization recommendations may also be “pre-approved” bythe user via, for example, one or more warning settings of an offlinebudgeting and/or quota management process, as already discussed.

FIG. 5 shows a computing device 50 (50 a-50 c) to budget data usage. Thecomputing device 50 may include a budget module 50 a to establish a datausage budget based on user input and/or historical usage data. The datausage budget may distinguish between usage types and distinguish betweenconnection types. For example, the budget module 50 a might designatethe usage types as high bandwidth usage and/or low bandwidth usage. Thebudget module 50 a may also designate the connection types as, forexample, a capped connection and/or a non-capped connection. Theillustrated computing device 50 also includes a monitor module 50 b tomonitor a data usage of one or more client devices in accordance withthe data usage budget. In one example, the monitor module 50 b obtainsmetering information from the client devices and/or one or more serviceproviders.

The computing device 50 may also include an optimization module 50 c toobtain approval for various optimization recommendations. Approval maybe obtained via one or more UI settings and/or warnings. For example,the optimization module 50 c may recommend a decrease in current datausage if the type of usage for the current data usage is a highbandwidth usage (e.g., downloading activity, streaming activity) and thetype of connection for the current data usage is a capped connection.The optimization module 50 c might also recommend an increase in currentdata usage if a billing cycle threshold is reached and a data usagethreshold is not reached, as already discussed. Other optimizations mayalso be conducted.

FIG. 6 illustrates a processor core 200 according to one embodiment. Theprocessor core 200 may be the core for any type of processor, such as amicro-processor, an embedded processor, a digital signal processor(DSP), a network processor, or other device to execute code. Althoughonly one processor core 200 is illustrated in FIG. 6, a processingelement may alternatively include more than one of the processor core200 illustrated in FIG. 6. The processor core 200 may be asingle-threaded core or, for at least one embodiment, the processor core200 may be multithreaded in that it may include more than one hardwarethread context (or “logical processor”) per core.

FIG. 6 also illustrates a memory 270 coupled to the processor 200. Thememory 270 may be any of a wide variety of memories (including variouslayers of memory hierarchy) as are known or otherwise available to thoseof skill in the art. The memory 270 may include one or more code 213instruction(s) to be executed by the processor 200 core, wherein thecode 213 may implement the method 32 (FIG. 4), already discussed. Theprocessor core 200 follows a program sequence of instructions indicatedby the code 213. Each instruction may enter a front end portion 210 andbe processed by one or more decoders 220. The decoder 220 may generateas its output a micro operation such as a fixed width micro operation ina predefined format, or may generate other instructions,microinstructions, or control signals which reflect the original codeinstruction. The illustrated front end 210 also includes registerrenaming logic 225 and scheduling logic 230, which generally allocateresources and queue the operation corresponding to the convertinstruction for execution.

The processor 200 is shown including execution logic 250 having a set ofexecution units 255-1 through 255-N. Some embodiments may include anumber of execution units dedicated to specific functions or sets offunctions. Other embodiments may include only one execution unit or oneexecution unit that can perform a particular function. The illustratedexecution logic 250 performs the operations specified by codeinstructions.

After completion of execution of the operations specified by the codeinstructions, back end logic 260 retires the instructions of the code213. In one embodiment, the processor 200 allows out of order executionbut requires in order retirement of instructions. Retirement logic 265may take a variety of forms as known to those of skill in the art (e.g.,re-order buffers or the like). In this manner, the processor core 200 istransformed during execution of the code 213, at least in terms of theoutput generated by the decoder, the hardware registers and tablesutilized by the register renaming logic 225, and any registers (notshown) modified by the execution logic 250.

Although not illustrated in FIG. 6, a processing element may includeother elements on chip with the processor core 200. For example, aprocessing element may include memory control logic along with theprocessor core 200. The processing element may include I/O control logicand/or may include I/O control logic integrated with memory controllogic. The processing element may also include one or more caches.

Referring now to FIG. 7, shown is a block diagram of a system 1000embodiment in accordance with an embodiment. Shown in FIG. 7 is amultiprocessor system 1000 that includes a first processing element 1070and a second processing element 1080. While two processing elements 1070and 1080 are shown, it is to be understood that an embodiment of thesystem 1000 may also include only one such processing element.

The system 1000 is illustrated as a point-to-point interconnect system,wherein the first processing element 1070 and the second processingelement 1080 are coupled via a point-to-point interconnect 1050. Itshould be understood that any or all of the interconnects illustrated inFIG. 7 may be implemented as a multi-drop bus rather than point-to-pointinterconnect.

As shown in FIG. 7, each of processing elements 1070 and 1080 may bemulticore processors, including first and second processor cores (i.e.,processor cores 1074 a and 1074 b and processor cores 1084 a and 1084b). Such cores 1074, 1074 b, 1084 a, 1084 b may be configured to executeinstruction code in a manner similar to that discussed above inconnection with FIG. 6.

Each processing element 1070, 1080 may include at least one shared cache1896 a, 1896 b. The shared cache 1896 a, 1896 b may store data (e.g.,instructions) that are utilized by one or more components of theprocessor, such as the cores 1074 a, 1074 b and 1084 a, 1084 b,respectively. For example, the shared cache 1896 a, 1896 b may locallycache data stored in a memory 1032, 1034 for faster access by componentsof the processor. In one or more embodiments, the shared cache 1896 a,1896 b may include one or more mid-level caches, such as level 2 (L2),level 3 (L3), level 4 (L4), or other levels of cache, a last level cache(LLC), and/or combinations thereof.

While shown with only two processing elements 1070, 1080, it is to beunderstood that the scope of the embodiments are not so limited. Inother embodiments, one or more additional processing elements may bepresent in a given processor. Alternatively, one or more of processingelements 1070, 1080 may be an element other than a processor, such as anaccelerator or a field programmable gate array. For example, additionalprocessing element(s) may include additional processors(s) that are thesame as a first processor 1070, additional processors) that areheterogeneous or asymmetric to processor a first processor 1070,accelerators (such as, e.g., graphics accelerators or digital signalprocessing (DSP) units), field programmable gate arrays, or any otherprocessing element. There can be a variety of differences between theprocessing elements 1070, 1080 in terms of a spectrum of metrics ofmerit including architectural, micro architectural, thermal, powerconsumption characteristics, and the like. These differences mayeffectively manifest themselves as asymmetry and heterogeneity amongstthe processing elements 1070, 1080. For at least one embodiment, thevarious processing elements 1070, 1080 may reside in the same diepackage.

The first processing element 1070 may further include memory controllerlogic (MC) 1072 and point-to-point (P-P) interfaces 1076 and 1078.Similarly, the second processing element 1080 may include a MC 1082 andP-P interfaces 1086 and 1088. As shown in FIG. 7, MC's 1072 and 1082couple the processors to respective memories, namely a memory 1032 and amemory 1034, which may be portions of main memory locally attached tothe respective processors. While the MC 1072 and 1082 is illustrated asintegrated into the processing elements 1070, 1080, for alternativeembodiments the MC logic may be discrete logic outside the processingelements 1070, 1080 rather than integrated therein.

The first processing element 1070 and the second processing element 1080may be coupled to an I/O subsystem 1090 via P-P interconnects 1076 1086,respectively. As shown in FIG. 7, the I/O subsystem 1090 includes P-Pinterfaces 1094 and 1098. Furthermore, I/O subsystem 1090 includes aninterface 1092 to couple I/O subsystem 1090 with a high performancegraphics engine 1038. In one embodiment, bus 1049 may be used to couplethe graphics engine 1038 to the I/O subsystem 1090. Alternately, apoint-to-point interconnect may couple these components.

In turn, I/O subsystem 1090 may be coupled to a first bus 1016 via aninterface 1096. In one embodiment, the first bus 1016 may be aPeripheral Component Interconnect (PCI) bus, or a bus such as a PCIExpress bus or another third generation I/O interconnect bus, althoughthe scope of the embodiments are not so limited.

As shown in FIG. 7, various I/O devices 1014 (e.g., cameras) may becoupled to the first bus 1016, along with a bus bridge 1018 which maycouple the first bus 1016 to a second bus 1020. In one embodiment, thesecond bus 1020 may be a low pin count (LPC) bus. Various devices may becoupled to the second bus 1020 including, for example, a keyboard/mouse1012, network controllers/communication device(s) 1026 (which may inturn be in communication with a computer network), and a data storageunit 1019 such as a disk drive or other mass storage device which mayinclude code 1030, in one embodiment. The code 1030 may includeinstructions for performing embodiments of one or more of the methodsdescribed above. Thus, the illustrated code 1030 may implement themethod 32 (FIG. 4), and may be similar to the code 213 (FIG. 6), alreadydiscussed. Further, an audio I/O 1024 may be coupled to second bus 1020,wherein the audio I/O 1024 may be used to establish a headsetconnection.

Note that other embodiments are contemplated. For example, instead ofthe point-to-point architecture of FIG. 7, a system may implement amulti-drop bus or another such communication topology. Also, theelements of FIG. 7 may alternatively be partitioned using more or fewerintegrated chips than shown in FIG. 7.

Additional Notes and Examples

Example 1 may include an apparatus to budget data usage, including abudget module to establish a data usage budget based on one or more ofuser input and historical usage data. The data usage budget maydistinguish between usage types and distinguish between connectiontypes. Additionally, the apparatus may include a monitor module tomonitor a data usage of one or more client devices in accordance withthe data usage budget.

Example 2 may include the apparatus of example 1, wherein the budgetmodule is to designate the usage types as one or more of a highbandwidth usage and a low bandwidth usage, and wherein the budget moduleis to designate the connection types as one or more of a cappedconnection and a non-capped connection.

Example 3 may include the apparatus of example 2, wherein the highbandwidth usage is to correspond to one or more of downloading activityand streaming activity, and wherein the low bandwidth usage is tocorrespond to messaging activity.

Example 4 may include the apparatus of example 2, wherein the cappedconnection is to correspond to one or more of a cellular connection anda private networking connection, and wherein the non-capped connectionis to correspond to a public networking connection.

Example 5 may include the apparatus of example 2, further including anoptimization module to recommend a decrease in current data usage if atype of usage for the current data usage is the high bandwidth usage anda type of connection for the current data usage is the cappedconnection.

Example 6 may include the apparatus of example 1, further including anoptimization module to recommend an increase in current data usage if abilling cycle threshold is reached and a data usage threshold is notreached.

Example 7 may include the apparatus of any one of examples 1 to 6,wherein the monitor module is to obtain metering information from atleast one of the one or more client devices to monitor the data usage.

Example 8 may include the apparatus of any one of examples 1 to 6,wherein the monitor module is to obtain metering information from one ormore service providers to monitor the data usage.

Example 9 may include a method of budgeting data usage, includingestablishing a data usage budget based on one or more of user input andhistorical usage data, wherein the data usage budget distinguishesbetween usage types and distinguishes between connection types. Themethod may also provide for monitoring a data usage of one or moreclient devices in accordance with the data usage budget.

Example 10 may include the method of example 9, further includingdesignating the usage types as one or more of a high bandwidth usage anda low bandwidth usage, and designating the connection types as one ormore of a capped connection and a non-capped connection.

Example 11 may include the method of example 10, wherein the highbandwidth usage corresponds to one or more of downloading activity andstreaming activity, and wherein the low bandwidth usage corresponds tomessaging activity.

Example 12 may include the method of example 10, wherein the cappedconnection corresponds to one of a cellular connection and a privatenetworking connection, and wherein the non-capped connection correspondsto a public networking connection.

Example 13 the method of example 10, further including recommending adecrease in current data usage if a type of usage for the current datausage is the high bandwidth usage and a type of connection for thecurrent data usage is the capped connection.

Example 14 may include the method of example 9, further includingrecommending an increase in current data usage if a billing cyclethreshold is reached and a data usage threshold is not reached.

Example 15 may include the method of any one of examples 9 to 14,wherein monitoring the data usage includes obtaining meteringinformation from at least one of the one or more client devices.

Example 16 may include the method of any one of examples 9 to 14,wherein monitoring the data usage includes obtaining meteringinformation from one or more service providers.

Example 17 may include at least one computer readable storage mediumincluding a set of instructions which, if executed by a computingdevice, cause the computing device to the method of any one of examples9 to 16.

Example 18 may include an apparatus to budget data usage, comprisingmeans for performing the method of any one of examples 9 to 16.

Techniques described herein may therefore enable users to registervarious data service accounts, such as home high speed cable modemaccounts, DSL accounts, cellular network (e.g., 3G/4G) accounts, Wi-Fiaccounts, MiFi (My Wi-Fi) accounts, wireless hotspots, etc., and setbudgets for high level categories such as watching movies, listening tomusic, surfing the Internet, e-mail messaging, and so forth.Additionally, suggestions may be offered to users on how to budget theirmonthly allotment of data usage. For example, suggestions may be basedon user shared Internet usage preferences, user profile information,current and past usage data, metrics from other consumers with similarconsumption patterns, devices and/or Internet services.

In addition, context aware actions may help users configure data usageas they switch between networks or devices based on the budgets of theirvarious data plans and access to free, unlimited (e.g., non-capped)connections. For example, if a user has movies or software in theirqueue scheduled for download, the client device may be configured toautomatically begin downloading whenever the device is within range of afree public networking connection with unlimited data usage.Alternatively, the client device might be configured to start locallycaching data while a user remains below a configured threshold of theirdata consumption budget on an available data plan.

Moreover, notifications may help users stay on budget throughconfigurable warnings, prompts and automatic enforcement actions. As anexample, before viewing a lengthy video, the client device may warn theuser that the length of the video will exceed current budget and/orpause the video once the budget is reached. Conversely, notificationsmay also be used to help a user “splurge” on high bandwidth activitiesin a timely fashion before a billing period ends, if usage is far belowthe budget. Notifications may also guide users to switch data plansbased on usage habits.

Various embodiments may be implemented using hardware elements, softwareelements, or a combination of both. Examples of hardware elements mayinclude processors, microprocessors, circuits, circuit elements (e.g.,transistors, resistors, capacitors, inductors, and so forth), integratedcircuits, application specific integrated circuits (ASIC), programmablelogic devices (PLD), digital signal processors (DSP), field programmablegate array (FPGA), logic gates, registers, semiconductor device, chips,microchips, chip sets, and so forth. Examples of software may includesoftware components, programs, applications, computer programs,application programs, system programs, machine programs, operatingsystem software, middleware, firmware, software modules, routines,subroutines, functions, methods, procedures, software interfaces,application program interfaces (API), instruction sets, computing code,computer code, code segments, computer code segments, words, values,symbols, or any combination thereof. Determining whether an embodimentis implemented using hardware elements and/or software elements may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherdesign or performance constraints.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that actually make the logic or processor.

Embodiments are applicable for use with all types of semiconductorintegrated circuit (“IC”) chips. Examples of these IC chips include butare not limited to processors, controllers, chipset components,programmable logic arrays (PLAs), memory chips, network chips, and thelike. In addition, in some of the drawings, signal conductor lines arerepresented with lines. Some may be different, to indicate moreconstituent signal paths, have a number label, to indicate a number ofconstituent signal paths, and/or have arrows at one or more ends, toindicate primary information flow direction. This, however, should notbe construed in a limiting manner. Rather, such added detail may be usedin connection with one or more exemplary embodiments to facilitateeasier understanding of a circuit. Any represented signal lines, whetheror not having additional information, may actually comprise one or moresignals that may travel in multiple directions and may be implementedwith any suitable type of signal scheme, e.g., digital or analog linesimplemented with differential pairs, optical fiber lines, and/orsingle-ended lines.

Example sizes/models/values/ranges may have been given, althoughembodiments are not limited to the same. As manufacturing techniques(e.g., photolithography) mature over time, it is expected that devicesof smaller size may be manufactured. In addition, well knownpower/ground connections to IC chips and other components may or may notbe shown within the figures, for simplicity of illustration anddiscussion, and so as not to obscure certain aspects of the embodiments.Further, arrangements may be shown in block diagram form in order toavoid obscuring embodiments, and also in view of the fact that specificswith respect to implementation of such block diagram arrangements arehighly dependent upon the platform within which the embodiment is to beimplemented, i.e., such specifics should be well within purview of oneskilled in the art. Where specific details (e.g., circuits) are setforth in order to describe example embodiments, it should be apparent toone skilled in the art that embodiments can be practiced without, orwith variation of, these specific details. The description is thus to beregarded as illustrative instead of limiting.

Some embodiments may be implemented, for example, using a machine ortangible computer-readable medium or article which may store aninstruction or a set of instructions that, if executed by a machine, maycause the machine to perform a method and/or operations in accordancewith the embodiments. Such a machine may include, for example, anysuitable processing platform, computing platform, computing device,processing device, computing system, processing system, computer,processor, or the like, and may be implemented using any suitablecombination of hardware and/or software. The machine-readable medium orarticle may include, for example, any suitable type of memory unit,memory device, memory article, memory medium, storage device, storagearticle, storage medium and/or storage unit, for example, memory,removable or non-removable media, erasable or non-erasable media,writeable or re-writeable media, digital or analog media, hard disk,floppy disk. Compact Disk Read Only Memory (CD-ROM), Compact DiskRecordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disk,magnetic media, magneto-optical media, removable memory cards or disks,various types of Digital Versatile Disk (DVD), a tape, a cassette, orthe like. The instructions may include any suitable type of code, suchas source code, compiled code, interpreted code, executable code, staticcode, dynamic code, encrypted code, and the like, implemented using anysuitable high-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language.

Unless specifically stated otherwise, it may be appreciated that termssuch as “processing,” “computing,” “calculating,” “determining,” or thelike, refer to the action and/or processes of a computer or computingsystem, or similar electronic computing device, that manipulates and/ortransforms data represented as physical quantities (e.g., electronic)within the computing system's registers and/or memories into other datasimilarly represented as physical quantities within the computingsystem's memories, registers or other such information storage,transmission or display devices. The embodiments are not limited in thiscontext.

The term “coupled” may be used herein to refer to any type ofrelationship, direct or indirect, between the components in question,and may apply to electrical, mechanical, fluid, optical,electromagnetic, electromechanical or other connections. In addition,the terms “first”, “second”, etc. may be used herein only to facilitatediscussion, and carry no particular temporal or chronologicalsignificance unless otherwise indicated.

As used in this application and in the claims, a list of items joined bythe term “one or more of” may mean any combination of the listed terms.For example, the phrases “one or more of A, B or C” may mean A; B; C; Aand B; A and C; B and C; or A, B and C.

Those skilled in the art will appreciate from the foregoing descriptionthat the broad techniques of the embodiments can be implemented in avariety of forms. Therefore, while the embodiments have been describedin connection with particular examples thereof, the true scope of theembodiments should not be so limited since other modifications willbecome apparent to the skilled practitioner upon a study of thedrawings, specification, and following claims.

We claim:
 1. An apparatus to budget data usage, comprising: a budgetmodule to establish a data usage budget based on one or more of userinput and historical usage data, wherein the data usage budget is todistinguish between usage types selected from at least low bandwidthusage and high bandwidth usage and distinguish between connection typesselected from at least a capped network connection with respect to datausage limits and a non-capped network connection with respect to datausage limits; and a monitor module to monitor a data usage of one ormore mobile client devices in accordance with the data usage budgetwherein the monitor module causes the mobile client device toautomatically cease high bandwidth usage, wherein the high bandwidthusage is to correspond to one or more of downloading activity orstreaming activity, when the monitor module detects that one or moremobile client devices is leaving a wireless non-capped networkconnection and resume high bandwidth usage when the monitor moduledetects that one or more mobile client devices is re-entering a wirelessnon-capped network connection.
 2. The apparatus of claim 1, wherein thelow bandwidth usage is to correspond to messaging activity.
 3. Theapparatus of claim 1, wherein the capped network connection is tocorrespond to one or more of a cellular connection and a privatenetworking connection, and wherein the non-capped network connection isto correspond to a public networking connection.
 4. The apparatus ofclaim 1, further including an optimization module to recommend adecrease in current data usage if a type of usage for the current datausage is the high bandwidth usage and a type of connection for thecurrent data usage is the capped network connection.
 5. The apparatus ofclaim 1, further including an optimization module to recommend anincrease in current data usage if a billing cycle threshold is reachedand a data usage threshold is not reached.
 6. The apparatus of claim 1,wherein the monitor module is to obtain metering information from atleast one of the one or more mobile client devices to monitor the datausage.
 7. The apparatus of claim 1, wherein the monitor module is toobtain metering information from one or more service providers tomonitor the data usage.
 8. A method of budgeting data usage, comprising:establishing a data usage budget based on one or more of user input andhistorical usage data, wherein the data usage budget distinguishesbetween usage types selected from at least low bandwidth usage and highbandwidth usage and distinguishes between connection types selected fromat least a capped network connection with respect to data usage limitsand a non-capped network connection with respect to data usage limits;and monitoring a data usage of one or more mobile client devices inaccordance with the data usage budget wherein the monitoring causes themobile client device to automatically cease high bandwidth usage,wherein the high bandwidth usage corresponds to one or more ofdownloading activity or streaming activity, when the monitoringdetermines that the one or more mobile client devices is leaving awireless non-capped network connection and resume high bandwidth usagewhen the monitoring determines that the one or more mobile clientdevices is re-entering a wireless non-capped network connection.
 9. Themethod of claim 8, wherein the low bandwidth usage corresponds tomessaging activity.
 10. The method of claim 8, wherein the wirelesscapped network connection corresponds to one of a cellular connectionand a private networking connection, and wherein the wireless non-cappednetwork connection corresponds to a public networking connection. 11.The method of claim 8, further including recommending a decrease incurrent data usage if a type of usage for the current data usage is thehigh bandwidth usage and a type of connection for the current data usageis the wireless capped network connection.
 12. The method of claim 8,further including recommending an increase in current data usage if abilling cycle threshold is reached and a data usage threshold is notreached.
 13. The method of claim 8, wherein monitoring the data usageincludes obtaining metering information from at least one of the one ormore mobile client devices.
 14. The method of claim 8, whereinmonitoring the data usage includes obtaining metering information fromone or more service providers.
 15. A non-transitory computer readablestorage medium comprising a set of instructions which, if executed by acomputing device, cause the computing device to: establish a data usagebudget based on one or more of user input and historical usage data,wherein the data usage budget is to distinguish between usage typesselected from at least low bandwidth usage and high bandwidth usage anddistinguish between connection types selected from at least a cappednetwork connection with respect to data usage limits and a non-cappednetwork connection with respect to data usage limits; and monitor a datausage of one or more mobile client devices in accordance with the datausage budget wherein the monitoring causes the mobile client device toautomatically cease high bandwidth usage, wherein the high bandwidthusage is to correspond to one or more of downloading activity orstreaming activity, when determining that the one or more mobile clientdevices is leaving a wireless non-capped network connection and resumehigh bandwidth usage when determining that the one or more mobile clientdevices is re-entering a wireless non-capped network connection.
 16. Thenon-transitory computer readable storage medium of claim 15, wherein thelow bandwidth usage is to correspond to messaging activity.
 17. Thenon-transitory computer readable storage medium of claim 15, wherein thecapped network connection is to correspond to one or more of a cellularconnection and a private networking connection, and wherein thenon-capped network connection is to correspond to a public networkingconnection.
 18. The non-transitory computer readable storage medium ofclaim 15, wherein the instructions, if executed, cause a computingdevice to recommend a decrease in current data usage if a type of usagefor the current data usage is the high bandwidth usage and a type ofconnection for the current data usage is the capped network connection.19. The non-transitory computer readable storage medium of claim 15,wherein the instructions, if executed, cause a computing device torecommend an increase in current data usage if a billing cycle thresholdis reached and a data usage threshold is not reached.
 20. Thenon-transitory computer readable storage medium of claim 15, wherein theinstructions, if executed, cause a computing device to obtain meteringinformation from at least one of the one or more client devices tomonitor the data usage.
 21. The non-transitory computer readable storagemedium of claim 15, wherein the instructions, if executed, cause acomputing device to obtain metering information from one or more serviceproviders to monitor the data usage.